Celebrating Successes

We talk a lot about culture in engineering. We discuss psychological safety, blameless postmortems, and fostering innovation. But how much do we actively celebrate wins? I remember one launch where, despite overcoming significant technical hurdles, the team just moved onto the next project without pausing to acknowledge the accomplishment. Morale noticeably dipped in the following sprint. It highlighted a crucial lesson: celebration isn’t just a nice-to-have—it’s a vital component of a high-performing culture, but it needs to be thoughtful, authentic, and tied to a deeper understanding of why it matters.

After two decades leading engineering teams, I’ve learned that celebration isn't about lavish parties or generic “good job” emails. It’s about creating a consistent rhythm of acknowledgment that builds a stronger, more engaged, and more resilient team.

Why Celebration Isn't Just Fluff

It's easy to dismiss celebrating as "soft skills." But consider this: engineering is inherently about solving difficult problems. It’s demanding, often frustrating, and failure is a constant companion. Without consistent acknowledgment of progress, teams can quickly become demoralized, innovation stifles, and burnout rises. In fact, studies show that teams with high levels of recognition experience 28.6% higher revenue and 31.3% lower employee turnover.

Celebrating isn't just about boosting morale (though it does that!). It's about:

• Reinforcing Desired Behaviors: What gets celebrated gets repeated. If you consistently acknowledge engineers who go the extra mile to mentor others, you’ll see more mentorship. If you highlight elegantly simple solutions, you encourage simplicity.
• Building Collective Efficacy: When a team overcomes a challenge and explicitly recognizes its achievement, it reinforces the belief that they can tackle future challenges. This shared sense of capability is crucial for innovation and resilience.
• Connecting Work to Impact: Engineers often work on pieces of a larger puzzle. Celebrating a launch or successful feature highlights how their individual contributions connect to a meaningful outcome for users or the business.

Beyond the Standard Playbook: Levels of Recognition

Too often, “celebration” defaults to a few predictable patterns: a team lunch, a shout-out in a meeting, or a gift card. These aren’t bad, but they lack depth and nuance. Here’s a framework I’ve found useful, moving beyond the superficial to address different types of achievements:

• Quick Wins (Daily/Weekly): These are small, incremental successes. Think: a tricky bug fixed, a challenging code review completed, or a helpful contribution to documentation. Recognition: Public acknowledgement in a daily stand-up, a quick “kudos” in Slack (we regularly highlight bug fixes in our #wins channel), or a dedicated channel for sharing small wins.
• Project Milestones (Monthly): Achieving significant milestones within a larger project deserves more attention. Recognition: A team lunch, a more detailed shout-out in a wider meeting, or a dedicated "milestone achieved" email outlining the team's accomplishments. For example, when we completed the beta release of our new API, we sent a team email detailing the challenges overcome and the key contributions of each member.
• Significant Achievements (Quarterly/Annually): Launching a major feature, significantly improving performance, or driving a key innovation are moments that demand significant recognition. Recognition: A dedicated team offsite, a presentation to leadership, or a public blog post highlighting the achievement and the individuals involved.
• Individual Contributions (Ongoing): Recognizing individuals for consistently going above and beyond, demonstrating exceptional skills, or embodying company values is crucial. Recognition: Performance reviews, promotions, opportunities for professional development, or simply a personal conversation acknowledging their contributions. We recently funded one engineer’s attendance at a specialized conference after recognizing their expertise in a critical technology.

Important Note: Recognition doesn't have to be monetary. In fact, often the most meaningful recognition is thoughtful and personalized.

Thinking From First Principles: What Truly Matters?

Let’s borrow a bit of wisdom from Peter Thiel – think about celebration from first principles. Thiel encourages us to break down complex problems into their fundamental truths. In this case, the fundamental truth is that human beings are motivated by recognition and appreciation. By asking “What would genuinely motivate my team?”, we move beyond simply copying what other companies do.

Here’s what I’ve learned:

• Authenticity is Key: A forced or insincere celebration is worse than no celebration at all.
• Focus on the "Why": Explain why the achievement matters. Connect it to the company's mission, the impact on users, or the team's overall goals.
• Make it Inclusive: Ensure everyone on the team feels valued and recognized for their contributions. Don’t just celebrate the "rockstars" – acknowledge the efforts of everyone involved. Be mindful of potential bias and actively seek out contributions from all team members.
• Don't Be Afraid to Get Creative: Think beyond traditional rewards. Could you give the team time to work on a side project? Could you send a personalized gift that reflects their interests?

Investing in a Culture of Appreciation

Celebrating successes isn't a one-time event; it's an ongoing investment in your team's culture. It requires intentionality, empathy, and a genuine appreciation for the hard work and dedication of your engineers. It's also important to acknowledge that leaders are often stretched thin, so starting small—even with a simple daily acknowledgment—is better than aiming for grand gestures and falling short. By moving beyond superficial gestures and focusing on what truly matters, you can build a team that is motivated, engaged, and capable of achieving extraordinary things.

Here's a 2x2 matrix visualizing the different levels of recognition:

Effort/Impact	Low	High
Frequency - Daily/Weekly	Bug fix shout-out, helpful documentation contribution	Successfully unblocking a teammate, mentoring a junior engineer
Frequency - Monthly/Quarterly	Completing a sprint goal, reaching a project milestone	Launching a new feature, significantly improving performance

This week, take the time to genuinely recognize one small win on your team. You’ll be surprised by the positive impact.